Quantos Peak
Adventure Associates Inc.
0
   |
Posted - 2016.03.20 05:26:45 -
[1] - Quote
Well, this is a mess isn't it? Of course there doesn't seem to be a single cause to all these issues, but I still find it hard to believe that a seemingly sudden increase of occurrence of this issue is completely unrelated with some change CCP have done at some point in the past few months. Perhaps it's a patch, or a server change.
Anyway, I've been experiencing this issue for a number of weeks now. I didn't make much of it for some time, so it's a bit hard to say exactly when this started to happen.
There are a couple of things that I have found.
First, numerous pinging and tracert tests have found no issues with my local server, or ISP connections. Some nodes along the way do show some packet loss, but none of it propagates to the end, and I'm always able to reach client.eveonline.com.
Now, there obviously are servers to reach other than client.eveonline.com (which is 87.237.34.202). Packets are being sent and received from 87.237.34.200 and 87.237.39.53. These are the ones that will fail when the connection is closed.
The type of connection to these two IPs is different. From what I can see the connection to 87.237.39.53 is SSL and consists of SYN packets over port 443. On the other hand, the connection to 87.237.34.200 is made over port 26000.
Just before the socket closes, these two connections will fail in different ways: http://i.imgur.com/DW5w8j6.png
The spurious retransmissions specifically are kind of a headache. I'm far from an expert in network analysis, but a brief read tells me that this type of retransmission happens when the source and destination do not agree on the state of the connection. In this case it looks like the CCP server is trying to reset a connection while I'm sending the retransmission for another. The fact that the retransmissions are spurious indicate that as far as my computer is concerned, that connection is valid and has already been acknowledged.
What exactly all of this means is hard for me to figure out. These TCP failures could certainly be related to something on my side or on CCP's, but they can be just as easily be related to something anywhere inbetween. There's just no way to tell. The bottom line simply is that at some point I'm sending information to the CCP server and it is either never received by CCP, or somehow handled incorrectly.
One thing I did try to mess around with is the limit of retransmissions that Windows will attempt before it considers a connection dead. By default, it will attempt 5 times, which happens over a pretty short period of time (roughly 15 seconds, but I believe the exact span of time depends on the quality of the connection). I was trying to find a way to increase the number of times it would attempt to retransmit, just to see if after a longer span of time I would get a response from CCP. However, while there is an easy regedit key to edit for this in Windows 7 and 8, it seems to be missing from Windows 10. I couldn't find a way to modify this in Windows 10. Now, maybe this is moot, as I'm not sure if this socket issue is OS-specific, but maybe it's worth taking a look at. |